%%
%%  ChkTeX v1.4, LaTeX documentation for ChkTeX program.
%%  Copyright (C) 1995-96 Jens T. Berger Thielemann
%%
%%  This program is free software; you can redistribute it and/or modify
%%  it under the terms of the GNU General Public License as published by
%%  the Free Software Foundation; either version 2 of the License, or
%%  (at your option) any later version.
%%
%%  This program is distributed in the hope that it will be useful,
%%  but WITHOUT ANY WARRANTY; without even the implied warranty of
%%  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
%%  GNU General Public License for more details.
%%
%%  You should have received a copy of the GNU General Public License
%%  along with this program; if not, write to the Free Software
%%  Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
%%
%%  Contact the author at:
%%              Jens Berger
%%              Spektrumvn. 4
%%              N-0666 Oslo
%%              Norway
%%              E-mail: <jensthi@ifi.uio.no>
%%
%% NOTE: This file is written in LaTeX, and should be compiled
%% before viewing. If you don't know how to do this, consult
%% your local TeX guru. If you don't possess LaTeX, you are
%% assumed to not need this program; so there's no text version
%% of this file...
%%
%% You may still be able to view the DVI or PostScript versions of
%% this file, though, they are included in the archive.
%%



\documentstyle[a4, array, tabularx, verbatim, multicol]{article}
\nonfrenchspacing
\newcounter{errornum}
\setcounter{errornum}{1}
\def\theerrornum{\arabic{errornum}}
\def\unknown{{\large\bf??}}
\def\jtbt{Jens~T. Berger~Thielemann}
\newcommand\Cmd[1]{``{\tt #1}''}
\def\rsrc{\Cmd{chktexrc}}
\def\chktex{Chk\TeX}

\def\LaTeXe{\LaTeX2${}_{\textstyle\varepsilon}$}

\newcolumntype{Y}{>{\raggedright\arraybackslash}X}

\newcommand\fmted[1]{{\noindent\large%
\begin{tabularx}{\linewidth}{lY}%
\bf Warning/error \theerrornum:  & \tt #1%
\end{tabularx}}%
\stepcounter{errornum}%
}

\newenvironment{errdesc}[1]{\noindent\fmted{#1}\begin{quote}}{\end{quote}}

\makeatletter
\@namedef{errdesc*}#1{\begin{errdesc}{\textit{#1}}}
\@namedef{enderrdesc*}{\end{errdesc}}
\@ifundefined{textit}{\gdef\textit#1{{\it #1}}}\relax
\makeatother


\newenvironment{errexam}
{
    \begin{samepage}
Example:\\*\vspace{-0.5cm}
    \begin{center}
}
{\end{center}\end{samepage}}

\title{\chktex\ v1.4}
\author{\jtbt}
\date{\today}

\begin{document}
\maketitle

\section{Introduction}

This program was written in frustration of that some constructs in
\LaTeX\ are sometimes non-intuitive, and easy to forget. It is {\em
  not\/} a replacement for the built-in checker in \LaTeX; however it
catches some typographic errors \LaTeX\ oversees. In other words, it
is Lint for \LaTeX. Filters are also provided for checking the \LaTeX\ 
parts of CWEB documents.

While written on an Amiga, it is written in ANSI C, so you can use
this at your UN*X/MS-DOS/whatever site also.  Full source included.

The program also supports output formats suitable for further
processing by editors or other programs, making errors easy to catch.
An ARexx script for interfacing with SCMSG (and via that, other
editors) is included. A special script for CygnusED and an
experimental script for GoldED is included. The program can also
produce output suitable for Emacs.

    The program itself  does not have any machine  requirements, Amiga
and MSDOS  binaries are  included.  Of  course, you'll  need ARexx and
SCMSG to benefit from the ARexx scripts.



\section{Legal stuff}

\chktex, documentation, installations scripts, CWEB filters and other
materials provided are copyright \copyright\ 1995--96 \jtbt, unless
explicitly stated otherwise.

This  program  is free software; you can redistribute it and/or modify
it  under  the terms of the GNU General Public License as published by
the  Free Software Foundation; either version 2 of the License, or (at
your option) any later version.

This  program  is  distributed in the hope that it will be useful, but
WITHOUT   ANY   WARRANTY;   without   even  the  implied  warranty  of
MERCHANTABILITY  or  FITNESS  FOR  A  PARTICULAR PURPOSE\@.  See the GNU
General Public License for more details.

You  should  have  received  a  copy of the GNU General Public License
along   with  this  program;  if  not,  write  to:
\begin{quote}
    The  Free  Software Foundation, Inc. \\
    675 Mass Ave \\
    Cambridge    \\
    MA 02139     \\
    USA
\end{quote}\newpage

\section{Feature list}
\begin{itemize}
\item Supports over 30 warnings. Warnings include:
  \columnseprule 0.1pt
  \begin{multicols}{2}
    \begin{flushleft}
      \begin{itemize}
      \item Commands terminated with space. Ignores \verb@\tt@, etc.
      \item Space in front of references instead of \verb@~@.
      \item Forgetting to group parenthesis characters when
        sub-/super\-scripting.
      \item Italic correction (``\verb@\/@'') mistakes (double,
        missing, unnecessary).
      \item Parenthesis and environment matching.
      \item Ellipsis detection; also checks whether to use
        \verb@\dots@, \verb@\cdots@ or \verb@\ldots@.
      \item Enforcement of normal space after abbreviation. Detect
        most abbreviations automagically.
      \item Enforcement of end-of-sentence space when the last
        sentence ended with capital letter.
      \item Mathmode on/off detection.
      \item Quote checking, both wrong types (\verb@"@) and wrong
        direction.
      \item Recommends splitting three quotes in a row.
      \item Searching for user patterns.
      \item Displays comments.
      \item Space in front of \verb@\label@ and similar commands.
      \item Use of ``x'' instead of $\times$ between numbers.
      \item Multiple spaces in input.
      \item Text which may be ignored.
      \item Mathematical operators typeset as variables.
      \end{itemize}
    \end{flushleft}
  \end{multicols}
\item Fully customizable. Intelligent resource format makes it
  possible to make \chktex\ respect your \LaTeX\ setup.  Even
  command-line options may be specified globally in the \rsrc\ file.
\item Supports \verb@\input@ command; both \TeX\ and \LaTeX\ version.
  Actually includes the files. \Cmd{TEXINPUTS}-equivalent search path.
\item Intelligent warning/error handling. The user may promote/mute
  warnings to suit his preferences. You may also mute warnings in the
  header of a file; thus killing much unwanted garbage.
\item Scripts included for checking CWEB files written in \LaTeX.
  (Requires perl v5).
\item Supports both \LaTeX\ 2.09 and \LaTeXe.
\item Flexible output handling. Has some predefined format, but lets
  the user specify his own format.  Uses a \Cmd{printf()} similar
  syntax. \Cmd{lacheck} compatible mode included for interfacing with
  the AUC TeX Emacs mode.
\item An ARexx script for interfacing with SCMSG, the SAS/C message
  browser, is included. Special script included for CygnusED/GoldED,
  for binding to hotkey.
\item Amiga Workbench support. Parameters may be passed by
  shift-clicking the \LaTeX\ files and setting the remaining options
  in the tooltypes.
\item Wildcard matching (Amiga only).  Matches file patterns
  internally, thus saving a lot of work.  This is, however,
  platform-specific code --- on UNIX boxes this is done by the shell.
\item Written in ANSI C\@. \Cmd{configure} script included for easy
  setup and installation on UNIX systems.
\end{itemize}

Still, it is important to realize that the output from \chktex\ is
only intended as a {\em guide\/} to fixing faults. However, it is by
no means always correct. This means that correct \LaTeX\ code may
produce errors in \chktex, and vice versa: Incorrect \LaTeX\ code may pass
silently through.


\subsection{New features}
Modifications and additions since v1.3:
\begin{itemize}
\item The whole subpart containing the error-checking routines has
  been restructured. This added the following benefits:
  \begin{itemize}
  \item We are now {\em much\/} more context-sensitive; warnings are
    to a much larger degree muted/promoted according to whether we are
    in math-mode or not.
  \item Detects math and verbatim environment (you may configure which
    are which), and acts accordingly.
  \end{itemize}
\item Yet more flexible resource format. UNIX systems may now have a
  {\em global\/} resource file; thus saving the individual users a lot
  of work installing the program.
\item You may now customize which dashlengths you allow in different contexts.
\item Removed that silly twirling baton which no-one used anyway.
\item A few more warnings:
\begin{itemize}
  \item Checks that quotes are used the right way.
  \item Checks for use of \Cmd{sin} instead of ``\verb@\sin@'' in mathmode and
    similar.
\end{itemize}
\item \Cmd{configure} script.
\item Compiles happily on MSDOS computers; binary included.
\item Output formats may now be specified globally in the \rsrc\ file now,
    for easy access.
\item Most other suggestions incorporated.
\end{itemize}

\section{Installation}

A few words on installation on various platforms:

\begin{description}
\item[Amiga:] Use the supplied Installer script.
\item[MS-DOS:] Copy the binary (\Cmd{ChkTeX.exe}) to somewhere in
  your path, and place the \rsrc\ file in the same directory. 
\item[UNIX:] Type \Cmd{configure}, \Cmd{make} and finally
  \Cmd{make~install}.  If you don't have superuser privileges and thus
  access to the default system areas, you should type
  \Cmd{configure~--help} to help you set up correct paths.

\item[Other platforms:] First of all, you have to copy the
  \Cmd{config.h.in} file to a file named \Cmd{config.h}.  Then, edit
  it to reflect your system.  Do the same with \Cmd{ChkTeX.h} (this
  file has been reduced significantly).  If you wish, you may define
  \Cmd{DATADIR} to the path you want the global resource file to be
  put.

  Now, I would suggest that you also take a peak at the \Cmd{OpSys.c}
  file first, and edit it appropiately, for more comfort.  This should
  not be necessary, though, at least not the first time.

  Finally, you may now compile and link all \verb@.c@ files.  Define
  \Cmd{HAVE\_CONFIG\_H} to 1 (on the command-line, for instance).  If
  the \Cmd{config.h} you wish to use has another name, define
  \Cmd{CONFIG\_H\_NAME} to that (in that case, don't define
  \Cmd{HAVE\_CONFIG\_H}.

  Put the directory path of the \rsrc\ file in a environment variable
  named \Cmd{CHKTEXRC}.  The files \Cmd{deweb.in} and \Cmd{chkweb.in}
  should be moved to a directory in your path.  These files may need
  further setup, as they haven't got the location of perl and csh
  initialized.

\end{description}
{\bf Note:} You {\em must} install the new \rsrc\ file; \chktex\ will
fail to function unless!

    After   doing   this,   you   may  enhance  \chktex'  behaviour  by
reading/editing the \rsrc\ file.


\section{Usage}

\subsection{\chktex}

Amiga v2.04+ users may wish to note that you may pass the files that
\chktex\ is to process by shift-clicking them. In addition, you may
specify the arguments as tooltypes to the main program icon, using the
{\sf Info} menu option. For instance, if you wish to make the `fancy'
output the default when starting from Workbench, enter the following
as a tooltype:
%
\begin{verbatim}
Verbosity=2
\end{verbatim}
%
We use the WB2Argv package (also developed by me, available on Aminet as 
\Cmd{dev/c/WB2Argv.lha}), and
will fold case until the \verb@=@ character, in tradition with the
case-insensitivity of Amiga OS\@.  In all other respects (and platforms), the
options listed below are case-sensitive.

\begin{description}
\item[\bf Template:] A UNIX-compliant template format follows:

\newcommand\Group[1]{\mbox{[#1]}}

  \begin{tabularx}\linewidth{lY}
    \tt chktex & \tt \Group{-hiqr} \Group{-v[0-3]} \Group{-l <rcfile>}
\Group{-[wemn] <[1-35]>} \Group{-d <number>}
\Group{-p <pseudoname>} \Group{-o <outputfile>}
\Group{-[btxgI][0|1]} file1 file2 \dots \\
  \end{tabularx}

\item[\bf Options:] These are the options \chktex\ currently accepts.
  Please note that single-lettered options requiring a numerical or no
  argument may be concatenated. E.g.\ saying ``{\tt -v0qb0w2}'' is the
  same as saying ``{\tt -v0 -q -b0 -w2}'', except for being less to
  type.

  Enough general talk; here's a rather detailed description of all
  options:
  \begin{description}
  \item[Misc.\ options:] General options which aren't related to some
    specific subpart of \chktex.
    \begin{description}
    \item[{\tt -h [--help]}] Gives you a command summary.
    \item[{\tt -i [--license]}] Shows distribution information.
    \item[{\tt -l [--localrc]}] Reads a resource-file formatted
      as the global resource-file \rsrc, in addition to the global
      resource-file. This option needs the name of the resource-file
      as a parameter. See also {\tt -g}.
    \item[{\tt -r [--reset]}] This will reset all settings to their
      defaults. This may be useful if you use the {\tt CMDLINE}
      directive in your \rsrc\ file, and wish to do something
      unusual.
    \item[{\tt -d [--debug]}] Given a numeric argument above zero,
      it will output some status information during run-time.
    \end{description}
  \item[Muting warning messages:] Controls whether and in what form
    error messages will appear.
    \begin{description}
    \item[{\tt -w [--warnon]}] Makes the message number passed as
      parameter a warning and turns it on.
    \item[{\tt -e [--erroron]}] Makes the message number passed as
      parameter an error and turns it on.
    \item[{\tt -m [--msgon]}] Makes the message number passed as
      parameter a message and turns it on. Messages are not counted.
    \item[{\tt -n [--nowarn]}] Turns the warning/error number passed
      as a parameter off.
    \end{description}
  \item[Output control flags:] Determines the appearance and
    destination of the error reports.
    \begin{description}
    \item[{\tt -q [--quiet]}] Shuts up about copyright information.
    \item[{\tt -o [--output]}] Normally, all errors are piped to
      stdout.  Using this option with a parameter, errors will be sent
      to the named file instead. Only information relative to the
      \LaTeX\ file will be sent to that file. Memory problems, etc.,
      will as as always be sent to {\tt stderr}. If a file with the
      name given already exists, it will be renamed to `{\tt
        foobar.bak}', {\tt foobar} being the name of the file.  See
      also {\tt -b}.
    \item[{\tt -f [--format]}] Specifies the format of the output.
      This is done using a format similar to {\tt printf()}, where we
      support the following specifiers:

      \newcommand{\Pf}[1]{\tt\%#1&}
      \begin{tabularx}\linewidth{cX}
        \bf Code & \bf Description \\
        \Pf{b} String to print {\bf b\/}etween fields (from {\tt -s}
        option). \\
        \Pf{c} {\bf C\/}olumn position of error. \\
        \Pf{d} Length of error ({\bf d\/}igit). \\
        \Pf{f} Current {\bf f\/}ilename.\\
        \Pf{i} Turn on {\bf i\/}nverse printing mode.\\
        \Pf{I} Turn off {\bf i\/}nverse printing mode.\\
        \Pf{k} {\bf k\/}ind of error (warning, error, message).\\
        \Pf{l} {\bf l\/}ine number of error.\\
        \Pf{m} Warning {\bf m\/}essage.\\
        \Pf{n} Warning {\bf n\/}umber.\\
        \Pf{u} An {\bf u\/}nderlining line (like the one which appears
        when using \Cmd{-v1}).\\
        \Pf{r} Part of line in front of error ($\mbox{`S'} - 1$).\\
        \Pf{s} Part of line which contains error ({\bf s\/}tring).\\
        \Pf{t} Part of line after error ($\mbox{`S'} + 1$).\\
      \end{tabularx}

      Other characters will be passed literally; thus you can say
      `{\tt \%\%}' to achieve a single percent sign in the output.
      Please note that we may introduce other specifiers in the future,
      so don't abuse this feature for other characters.
      
      Also, note that we do {\em not\/} support field lengths (yet).
      This may come in the future, if I get the time\dots
      
      The {\tt -v} command is implemented by indexing into the \rsrc\
      file; read that for seeing how each format is implemented. If
      you find yourself using a particular format often by using the
      -f switch, consider putting it in the \rsrc\ file instead.

    \item[{\tt -v [--verbosity]}] Specifies how much and how you
      wish the error reports to be displayed. This is specified in the
      \rsrc\ file; we'll list the default values below. If you wish,
      you may thus edit the \rsrc\ file to add or modify new formats.

      By default, we'll choose format 1 (that is, the {\em second\/}
      entry in the \rsrc\ file).

      \begin{description}
      \item[0] Will show the information in a way that should be
        suitable for further parsing by {\tt awk}, {\tt sed} or
        similar.  The format is as follows:
        \begin{verbatim}
File:Line:Column:Warning number:Warning message
        \end{verbatim}
        The colons may be replaced with another string; use the
        \verb@-s@ switch for this.

        This format will also turn off any twirling baton's, and other
        things which make the program unsuitable for pipes and batch
        scripts. As the program does yet not output all errors in
        quite order, this output format is also suitable for piping
        through `{\tt sort}'.
      \item[1] Shows the information in a way which is more
        comprehensible for humans, but which still doesn't need
        anything but a glass tty.
      \item[2] Shows the information in a fancy way, using escape
        codes and stuff. It is the indeed most readable of all
        modes; however, it needs proper set up of the `{\tt
          chktex.h}' file.
      \item[3] Shows the information suitable for parsing by Emacs;
        this is the same format as {\tt lacheck} uses. More formally,
        it is the following:
\begin{verbatim}
"File", line Line: Warning message
\end{verbatim}

        To utilize this, type \verb@M-x compile RET@. Delete whatever
        is written in the minibuffer, and type
        \verb@chktex.pl -v3 texfile.tex@, and you should be able to
        browse through the
        error messages.  Use \verb@C-x `@ to parse the messages.
      \item[4] More or less the same as \verb@-v3@, but also includes
        information on where the error actually was found. Takes somewhat
        longer time to parse, but much more informative in use.
      \end{description}
      The default is mode 1, using {\tt -v} without any parameter
      will give you mode 2.

    \item[{\tt -p [--pseudoname]}] With this switch, you can provide
      the filename which will be used when we report the errors. This
      may be useful in scripts, especially when doing pipes. It is in
      other words similar to C's \verb@#line@ directive.

      We will only assume this name for the uppermost file; files that
      this one in turn \verb@\input@ are presented under their original
      names. This seems most logical to me.

    \item[{\tt -s [--splitchar]}] String to use instead of the
      colons when doing {\tt -v0}; e.g.\ this string will be output
      between the fields.

    \end{description}
  \item[Boolean switches:] Common for all of these are that they
    take an optional parameter.  If it is {\tt 0}, the feature will
    be disabled, if it is {\tt 1}, it will be enabled. All these
    features are on by default; and are toggled if you don't give
    any parameter.

    \begin{description}
    \item[{\tt -b [--backup]}] If you use the {\tt -o} switch, and the
      named outputfile exists, it will be renamed to {\tt
        filename.bak}.
    \item[{\tt -I [--inputfiles]}] Execute \verb@\input@ statements;
      e.g.\ include the file in the input. Our input parsing does of
      course nest; we use an input-stack to keep track of this.
    \item[{\tt -H [--headererr]}] Show errors found in front of the
      \verb@\begin{document}@ statement. Some people keep       {\em
          lots\/} of pure \TeX\ code there, which errors can't be
        detected reliably (in other words, we will in most cases just
        produce a lot of garbage).
      \item[{\tt -g [--globalrc]}] Read in the global resource file.
        This switch may be useful together with the {\tt -l} option.
    \item[{\tt -t [--tictoc]}] Display a twirling baton, to show
      that we're working. {\tt -v0} does an {\tt -t0}, too, as it
      assumes that the user then uses the program non-interactively.
      This is now a no-op.
    \item[{\tt -x [--wipeverb]}] Ignore the `\verb@\verb@' command
      found within the \LaTeX\ file and its argument is completely
      by the checking routines.  This is done by simply overwriting
      them.  If you somehow don't like that (for instance, you would
      like to count brackets inside those commands, too), use this
      switch.
    \end{description}
  \end{description}
\end{description}

If you don't specify any input \LaTeX-files on the commandline, we'll
read from {\tt stdin}.  To abort {\tt stdin} input, press $\fbox{\tt
  Ctrl} + \fbox{\tt\string\ }$ on the Amiga; on UNIX $\fbox{\tt Ctrl} +
\fbox{\tt D}$.  By default, we're using the 1994 version of GNU's {\tt
  getopt()} routine.  For those of you who have only used the Amiga's
ReadArgs(), here are some quick instructions:

\begin{itemize}
\item Options may be given in any order; the names of the \LaTeX-files
  do not have to be the last arguments. This behaviour may be turned
  off by creating an environment variable named
  `\verb@POSIXLY_CORRECT@'.
\item The special argument `\verb@--@' forces an end of
  option-scanning.
\item Long-named options begin with `\verb@--@' instead of `\verb@-@'.
  Their names may be abbreviated as long as the abbreviation is unique
  or is an exact match for some defined option. If they have an
  argument, it follows the option name in the argument, separated from
  the option name by a `=', or else the in next argument.
\end{itemize}

You should also take a look at the \rsrc\ file. The method for finding
has been changed, it is now done as follows:
\begin{enumerate}
    \item Look for it in the current directory.
    \item Look for it in the directory pointed to by the environment
          variable {\tt CHKTEXRC}.
    \item Look in the following directories:

\begin{tabular}{ll}
    \bf Machine & \bf Directory \\
    2.04+ Amiga & {\tt ENV:}   \\
    1.3 Amiga   & {\tt S:}      \\
    UNIX        & {\tt \$HOME}   \\
\end{tabular}
\end{enumerate}
If \chktex\ fails to find the \rsrc\ file it any of these places, it
will look for it in the directory you specified as \verb@DATADIR@ when
installing it, but then omitting the leading dot. Usually, this
evaluates to \verb@/usr/local/share/chktexrc@ or
\verb@/usr/local/lib/chktexrc@.

It  should  be  rather self-explanatory, and should help you customize the
program to your own needs.

\subsection{ChkWEB}

This  C-shell  script is provided for checking CWEB files.  The template is
as follows:
%
\begin{verbatim}
chkweb file1 file2 ...
\end{verbatim}

As you may see from the script, it is only a trivial interface towards
\Cmd{deweb} and \chktex.  It does currently not support any options on the
command line; the only intelligence it features is that it will try to
append \verb@.w@ to filenames it can't find.

Please note that the \Cmd{deweb} Perl5 script does in fact preserve
linebreaks, and should also mostly keep column positions correct.
\verb@|...|@ uses are currently not dealt with, though.

The \Cmd{deweb} script is supposed to deal with all correct CWEB
escape sequences; if I have accidentally omitted some, please let me
know.

\section{Explanation of error messages}
Below is a description of all error-messages \chktex\ outputs.
Error messages set in {\it italic type\/} are turned off by default.

\smallskip
\begin{errdesc}{Command terminated with space.}

  You tried to terminate a command with a blank space.  Usually, this
  is an error as these are ignored by \LaTeX. In most cases, you would
  like to have a real space there.

\begin{errexam}
\verb@\LaTeX@\underline{ }\verb@is a typesetter.@ \\*
\LaTeX is a typesetter. \\*
\smallskip
\verb@\LaTeX\ is a typesetter.@ \\*
      \LaTeX\ is a typesetter.  \\*
\end{errexam}
\end{errdesc}

\begin{errdesc}{Non-breaking space (`\~{ }') should have been used.}

  When reading a document, it is not very pretty when references are
  split across lines.  If you use the \verb@~@ character, \LaTeX\ will
  assign a very high penalty for splitting a line at that point.
  \chktex\ issues this warning if you have forgot to do this.

\begin{errexam}
\verb@Please refer to figure@\underline{ }\verb@\ref{foo}.@ \\*
Please refer to figure 11.                \\* % Gotta cheat here! :)
\smallskip
\verb@Please refer to figure~\ref{foo}.@ \\*
Please refer to figure~11.  \\*
\end{errexam}
\end{errdesc}

\begin{errdesc}{You should enclose the previous  parenthesis with `\{\}'.}

  This is a warning which you may ignore, but for maximum aestethic
  pleasure, you should enclose your bracket characters with `\{\}'s.

\begin{errexam}
\verb@$@\underline{ }\verb@[(ab)^{-1}]@\underline{ }\verb@\^{-2}$@ \\*
$[(ab)^{-1}]^{-2}$ \\*
\smallskip
\verb@${[{(ab)}^{-1}]}^{-2}$@ \\*
${[(ab)^{-1}]}^{-2}$ \\*
\end{errexam}
\end{errdesc}

\begin{errdesc}{Italic correction (`{\string\/}') found in non-italic buffer.}
  If you try to use the \verb@\/@ command when \chktex\ believes that
  the buffer is not outputted as italic, you'll get this warning.

\begin{errexam}
\verb@This is an@\underline{\tt\string\/}\verb@ example@ \\*
This is an\/ example. \\*
\smallskip
\verb@This is an example.@ \\*
This is an example. \\*
\end{errexam}
\end{errdesc}

\begin{errdesc}{Italic correction (`{\tt\string\/}') found more than once.}

  If the buffer is italic, and you try to use the \verb@\/@ command
  more than once, you'll get this warning.

\begin{errexam}
\verb@This {\it example\/@\underline{\tt\string\/}\verb@} is not amusing.@ \\*
This {\it example\/\/} is not amusing. \\*
\smallskip
\verb@This {\it example\/} is not amusing.@  \\*
This {\it example\/} is not amusing. \\*
\end{errexam}
\end{errdesc}

\begin{errdesc}{No italic correction (`{\tt\string\/}') found.}

  You get this error if \chktex\ believes that you are switching from
  italic to non-italic, and you've forgot to use the \verb@\/@ command
  to insert that extra little spacing. If you use the {\tt em} option,
  you may ignore this warning.

\begin{errexam}
\verb@This {\it example@\underline{ }\verb@} is not amusing, either.@ \\*
This {\it example} is not amusing, either. \\*
\smallskip
\verb@This {\it example\/} is not amusing, either.@ \\*
This {\it example\/} is not amusing, either. \\*
\end{errexam}
\end{errdesc}

\begin{errdesc}{Accent command `command' needs  use of `command'.}

  If you're using accenting commands, `i' and `j' should lose their
  dots before they get accented. This is accomplished by using the
  \verb@\i@, \verb@\j@, \verb@\imath@ and \verb@\jmath@ command.


\begin{errexam}
\verb@This is an example of use of accents: \'{@\underline{\tt i}\verb@}.@ \\*
This is an example of use of accents: \'{i}. \\*
\smallskip
\verb@This is an example of use of accents: \'{\i}.@ \\*
This is an example of use of accents: \'{\i}. \\*
\end{errexam}
\end{errdesc}

\begin{errdesc}{Wrong length of dash may have been used.}
  This warning suggests that a wrong number of dashes may have been
  used.  It does this by classifying the dash according to the the
  character in front and after the dashes.

  If they are of the same type, \chktex\ will determine which keyword
  to use in the \rsrc\ file. If not, it will shut up and accept that
  it doesn't know.

  \begin{tabular}{ll}
    \bf Character type & \bf Keyword in \rsrc\ file \\*
    Space & \tt WordDash \\*
    Number & \tt NumDash \\*
    Alphabetic character & \tt HyphDash \\*
  \end{tabular}

  This is more or less correct, according to my references.  Hopefully
  this check can be even more improved (suggestions?).

\begin{errexam}
\verb@It wasn't anything @\underline{\tt-}\verb@ just a 2@\underline
{\tt---}\verb@3 star@\underline{\tt--}\verb@shots.@ \\*
It wasn't anything - just a 2---3 star--shots. \\*
\smallskip
\verb@It wasn't anything --- just a 2--3 star-shots@ \\*
It wasn't anything --- just a 2--3 star-shots. \\*
\end{errexam}
\end{errdesc}

\begin{errdesc}{`\%s' expected, found  `\%s'.}

  You get this warning when you try to mix brackets or environments
  --- \chktex\ expect to find matching brackets/environments in the
  same order as their opposites were found.  While bracket matching is
  not an explicit error, it is usually a sign that something is wrong.

\end{errdesc}

\begin{errdesc}{Solo `\%s' found.}

  This warning is triggered if we find a single, {\em closing\/}
  bracket or environment.  While bracket matching is not an explicit
  error, it is usually a sign that something is wrong.

\end{errdesc}

\begin{errdesc}{You should use `\%s' to achieve  an ellipsis.}

  Simply typing three `.' in a row will not give a perfect spacing
  between the `.'s. The \verb@\dots@ is much more suitable for this.

  In math mode, you should also distinguish between \verb@\cdots@ and
  \verb@\ldots@; take a look at the example below.

\begin{errexam}
\newcommand\td{\underline{\tt...}}
\verb@Foo@\td\verb@bar. $1,@\td\verb@,3$. $1+@\td\verb@+3$. $1,@%
\underline{\tt\string\cdots}\verb@,3$.@ \\*
Foo...bar. $1,...,3$. $1+...+3$. $1,\cdots,3$.  \\*
\smallskip
\verb@Foo\dots bar. $1,\ldots,3$. $1+\cdots+3$. $1,\ldots,3$.@ \\*
Foo\dots bar. $1,\ldots,3$. $1+\cdots+3$. $1,\ldots,3$. \\
\end{errexam}
\end{errdesc}

\begin{errdesc}{Interword spacing (`{\tt\string\ }') should perhaps be used.}

  One of the specified abbreviations were found. Unless you have
  previously said \verb@\frenchspacing@, you'll have incorrect
  spacing, which one should avoid if possible.

\begin{errexam}
\verb@This is an example, i.e.@\underline{ }\verb@an demonstration.@ \\*
This is an example, i.e. an demonstration.        \\*
\smallskip
\verb@This is an example, i.e.\ an demonstration.@   \\*
This is an example, i.e.\ an demonstration.        \\*
\end{errexam}
\end{errdesc}

\begin{errdesc}{Intersentence spacing (`{\tt\string\@}') should perhaps be used.}

  \LaTeX' detection of whether a period ends a sentence or not, is
  only based upon the character in front of the period. If it's
  uppercase, it assumes that it does not end a sentence. While this
  may be correct in many cases, it may be incorrect in others.
  \chktex\ thus outputs this warning in every such case.

\begin{errexam}
\verb@I've seen an UFO!@\underline{ }\verb@Right over there!@ \\*
I've seen an UFO! Right over there!        \\*
\smallskip
\verb+I've seen an UFO\@! Right over there!+ \\*
I've seen an UFO\@! Right over there!        \\*
\end{errexam}
\end{errdesc}

\begin{errdesc}{Could not find argument for  command.}

  \chktex\ will in some cases need the argument of a function to
  detect an error. As \chktex\ currently processes the \LaTeX\ file on
  a line-by-line basis, it won't find the argument if the command
  which needed it was on the previous line. On the other hand, this
  {\em may\/} also be an error; you ought to check it to be safe.

\begin{errexam}
\verb@$\hat$@ \\*
This will give a \LaTeX\ error\dots  \\*
\smallskip
\verb@$\hat{a}$@ \\*
$\hat{a}$        \\*
\end{errexam}
\end{errdesc}

\begin{errdesc}{No match found for `\%s'.}

  This warning is triggered if we find a single, {\em opening\/}
  bracket or environment.  While bracket matching is not an explicit
  error, it is usually a sign that something is wrong.

\end{errdesc}

\begin{errdesc}{Mathmode still on at end of LaTeX  file.}

  This error is triggered if you at some point have turned on
  mathmode, and \chktex\ couldn't see that you remembered to turn it
  off.

\end{errdesc}

\begin{errdesc}{Number of `character' doesn't match the number of `character'!}

  Should be self-explanatory. \chktex\ didn't find the same number of
  an opening bracket as it found of a closing bracket.

\end{errdesc}

\begin{errdesc}{You should use either `` or '' as  an alternative to `\,"\,'.}
  Self-explanatory. Look in the example, and you'll understand why.

\begin{errexam}
\verb@This is an @\underline{"}\verb@example@\underline{"} \\*
This is an "example" \\*
\smallskip
\verb@This is an ``example''@ \\*
This is an ``example'' \\*
\end{errexam}
\end{errdesc}

\begin{errdesc}{You should use "'" (ASCII 39)  instead  of
    "'" (ASCII 180).} On some keyboards you might get the wrong quote.
  This quote looks, IMHO, {\em ugly\/} compared to the standard
  quotes, it doesn't even come out as a quote!  Just see in the
  example.


\begin{errexam}
% Sorry, had to cheat - the 's aren't really 180's, they look like this: �
%
\verb@``There@\underline{\tt '}\verb@s quotes and there@\underline{\tt  '}\verb@s quotes@
\underline{\tt ''} \\* % ''
``There�s quotes and there�s quotes�� \\* % ''
\smallskip
\verb@``There's quotes and there's quotes''@ \\*
``There's quotes and there's quotes'' \\*
\end{errexam}
\end{errdesc}

\begin{errdesc}{User-specified pattern found.}
  A keyword you've specified using {\tt USERWARN} in the \rsrc\ file,
  has been found.
\end{errdesc}

\begin{errdesc*}{This command might not be intended.}
  I implemented this because a friend of mine kept on making these
  mistakes.  Easily done if you haven't gotten quite into the syntax
  of \LaTeX.

\begin{errexam}
\verb@\LaTeX\ is an extension of \TeX@\underline{\tt\string\.}\verb@ Right?@ \\*
\LaTeX\ is an extension of \TeX\. Right? \\*
\smallskip
\verb@\LaTeX\ is an extension of \TeX. Right?@ \\*
\LaTeX\ is an extension of \TeX. Right? \\*
\end{errexam}
\end{errdesc*}

\begin{errdesc*}{Comment displayed.}
  \chktex\ dumps all comments it finds, which in some cases is useful.
  I usually keep all my notes in the comments, and like to review them
  before I ship the final version. For commenting out parts of the
  document, the {\tt comment} environment is better suited.

\end{errdesc*}


\begin{errdesc}{Either ''{\tt\string\,}' or '{\tt\string\,}'' will look  better.}

  This error is generated whenever you try to typeset three quotes in
  a row; this will not look pretty, and one of them should be
  separated from the rest.

\begin{errexam}
\underline{\tt```}\verb@Hello', I heard him said'', she remembered.@ \\*
```Hello', I heard him said'', she remembered. \\*
\smallskip
\verb@``\,`Hello', I heard him said'', she remembered.@ \\*
``\,`Hello', I heard him said'', she remembered.
\end{errexam}
\end{errdesc}

\begin{errdesc}{Delete this space to maintain correct  pagereferences.}

  This message, issued when a space is found in front of a
  \verb@\index@, \verb@\label@ or similar command (can be set in the
  \rsrc\ file).  Sometimes, this space may cause that the word and the
  index happens on separate pages, if a pagebreak happens just there.

  You might also use this warning to warn you about spaces in front of
  footnotes; however, the warning text may not be entirely correct
  then.

\begin{errexam}
\verb@Indexing text@\underline{ }\verb@\index{text} is fun!@ \\*
\smallskip
\verb@Indexing text\index{text} is fun!@ \\*
\end{errexam}
\end{errdesc}

\begin{errdesc}{You might wish to put this between a pair of `\{\}'}

  This warning is given whenever \chktex\ finds a `{\tt \^{ }}' or a
  {\tt \_} followed by either two or more numberic digits or two or
  more alphabetic characters.  In most situations, this means that
  you've forgotten some \{\}'s.

\begin{errexam}
\verb@$5\cdot10^@\underline{10}\verb@$@ \\*
$5\cdot10^10$ \\*
\smallskip
\verb@$5\cdot10^{10}$@ \\*
$5\cdot10^{10}$
\end{errexam}
\end{errdesc}

\begin{errdesc}{You ought to remove spaces in front of punctuation.}

  This warning is issued if \chktex\ finds space in front of an
  end-of-sentence character.

\begin{errexam}
\verb@Do you understand @\underline{ }\verb@?@ \\*
Do you understand ? \\*
\smallskip
\verb@Do you understand?@ \\*
Do you understand? \\*
\end{errexam}
\end{errdesc}

\begin{errdesc}{Could not execute LaTeX command.}

  Some \LaTeX\ commands will be interpreted by \chktex; however, some
  of them are sensible to errors in the \LaTeX\ source. Most notably,
  the \verb@\input@ command relies on that the input file exists\dots

\end{errdesc}

\begin{errdesc}{Don't use {\tt\string\/} in front of small punctuation.}

  Italic correction should generally {\em not\/} be used in front of
  small punctuation characters like `.' and `,'; as it looks better
  when the preceding italic character leans ``over'' the punctum or
  comma.

\begin{errexam}
\verb@It is just a {\it test@\underline{\tt\string\/}\verb@}, don't think anything else.@ \\*
It is just a {\it prototype\/}, don't think anything else. \\*
\smallskip
\verb@It is just a {\it test}, don't think anything else.@ \\*
It is just a {\it prototype}, don't think anything else.
\end{errexam}
\end{errdesc}

\begin{errdesc}{\${\string\times}\$ may look prettier here.}
  In ASCII environments, it is usual to use the `x' character as an
  infix operator to denote a dimension. The mathemathical symbol
  $\times$provided by the \verb@$\times$@ command is better suited for
  this.

\begin{errexam}
\verb@The program opens a screen sized 640@\underline{\tt x}\verb@200 pixels.@ \\*
The program opens a screen sized 640x200 pixels. \\*
\smallskip
\verb@The program opens a screen sized $640\times200$ pixels.@ \\*
The program opens a screen sized $640\times200$ pixels.
\end{errexam}
\end{errdesc}

\begin{errdesc*}{Multiple spaces detected in output.}

  This warning, intended for the novice, will remind you that even if
  you {\em type} multiple spaces in your input, only a single space
  will come out. Some ways to come around this is listed below.

\begin{errexam}
\verb@White           is a beautiful colour.@ \\*
White           is a beautiful colour. \\*
\smallskip
\verb@White~~~~~{ }{ }{ }\ \ \ is a beautiful colour.@ \\*
White~~~~~{ }{ }{ }\ \ \ is a beautiful colour. \\
\end{errexam}
\end{errdesc*}

\begin{errdesc}{This text may be ignored.}

  Certain implementations of the \verb@verbatim@ environment and
  derivations of that, ignore all text after \verb@\end{verbatim}@.
This will warn you of this.


\end{errdesc}

\fmted{Use ` to begin quotation, not '.}\hfill\\
\fmted{Use ' to end quotation, not `.}\hfill\\
\begin{errdesc}{Don't mix quotes.}

  Proper quotations should start with a \verb@`@ and end with a
  \verb@'@; anything else isn't very pretty. Both these warnings are
  relative to this; look in the example below.

\begin{errexam}
\verb@There are @\underline{\tt`'}%
\verb@examples'' and there are ``examples@\underline{\tt``}\verb@.@ \\*
There are `'examples'' and there are ``examples``. \\*
\smallskip
\verb@There are ``examples'' and there are ``examples''.@ \\*
There are ``examples'' and there are ``examples''.
\end{errexam}
\end{errdesc}

\begin{errdesc}{You should perhaps use `cmd' instead.}
  Most mathematical operators should be set as standard roman font,
  instead of the math italic \LaTeX\ uses for variables. For many
  operators, \LaTeX\ provides a pre-defined command which will typeset
  the operator correctly. Look below for an illustration of the point.

\begin{errexam}
\verb@$@\underline{\tt sin}\verb@^2 x + @\underline{\tt cos}\verb@^2 x = 1$@ \\*
$sin^2 x + cos^2 x= 1$ \\*
\smallskip
\verb@$\sin^2 x + \cos^2 x = 1$@ \\*
$\sin^2 x + \cos^2 x = 1$
\end{errexam}
\end{errdesc}

\section{Bugs}

No fatal ones, I think, but the program currently has some problems when a
\LaTeX\ command/parameter stretch over a two lines --- some extra spaces
may be inserted into the input.  I regard the program as fairly well
tested; using the SAS/C {\tt cover} utility I was able to make sure that
approximately 95\% of the code has actually been run successfully in the
final version.  This does indeed leave some lines; most of these are
procedure terminating brackets or `can't happen' lines, though.

We've got some problems when isolating the arguments of a command.
Although improved, it will certainly fail in certain cases; \chktex\
can for instance not handle arguments stretching over two lines. This
also means that \Cmd{WIPEARG} entries in the \rsrc\ file will only
have the first half of their argument wiped if the argument stretches
over two lines.
Currently, this should cause nothing but a few extra warnings.

There is also a small bug which will occur if you try to type the
following:
\begin{verbatim}
Please take a look at ChkTeX.DVI. Please.
\end{verbatim}

\chktex\ will then report that you both should use interword spacing and
intersentence spacing.  This happens whenever you use an uppercase
abbreviation. Will be fixed --- but it requires some restructuring of
the program.

Before submitting a bug report, please first see whether the problem can be
solved by editing the \rsrc\ file appropiately.

\section{Future plans}

In a somewhat prioritized sequence, this is what I'd like to put into the
program --- if I have the time.

\begin{itemize}
\item Support for regular expressions as user patterns. Have the code,
  just have to interface to it.

\item Differentiate whether strings in the resource file should be
  checked case-sensitively or case-insensitively; we do now only do
  a dumb enforcement of what seems most practical for each keyword.

\item Clean up the italic checking; it doesn't nest braces (in fact,
  that's why it magically works with \LaTeXe\dots).

\item Probably some more warnings/errors; just have to think them out
  first.  Suggestions are appreciated --- I've ``stolen'' most that
  lacheck provides, and am running out of ideas, really.

\item Fix a few more bugs. :-)

\item Put some garbage collecting into the thing. We're buffering
  almost one half of the lines in the file for the life of the
  program.  99\% of these can be expunged {\em much\/} earlier.
  However, if you're dealing with so large files that you get
  out-of-mem errors, please consider splitting and using \verb@\input@
  instead.

  Besides; if \chktex\ runs out of memory when processing your files,
  \LaTeX\ will indeed do the same!

\item Rewrite the thing in Perl? Get regexp's for free, at least.
  I have received positive reactions on this; however I feel that Perl
  hasn't the structural support C gives the programmer (I'm especially
  thinking of \verb@struct@'s now, which simply doesn't feel the same
  when realized as an associative array).
\end{itemize}

\section{Notes}

\subsection{Wish to help?}

As most other living creatures, I have only a limited amount of time. If
you like \chktex\ and would like to help improving it, here's a few things
I would like to receive. Think of it as giftware --- if you like it, you
help improving it. The following ideas are given:

\begin{itemize}
\item Help me port the program! This is a prioritized one. It's no fun
  writing ANSI C when people haven't got a C compiler. 

  Of course, I'll provide whatever help necessary to modify the sources
  to fit to the new platform. Take contact if you're interested. I will
  include your compiled binary in the distribution, and give you
  credit where appropiate.

\item Reports on problems configuring and compiling \chktex\ on supported
  systems are welcomed.

\item Information on the \Cmd{\_doprnt} function; prototypes and use. 
  I've understood that not all systems support the \Cmd{vfprintf} 
  function (which \chktex\ uses a lot); however, some of them have
  a similar function (according to the Autoconf manual).

  I would like to receive any information on this; as I would like to
  create an interface towards that function.

\item Filters for other file formats. I do believe that there are
  several formats using \LaTeX\ for its formatting purposes, combining
  that with something else. If you can write a program or script which
  filters everything away but the \LaTeX\ code, it will surely be
  appreciated (and included). Look at the \verb@deweb@ script to see what I mean.

\item Arexx interfaces for other editors are also welcomed; these
  should be rather fast to write.  They should to the following:
  \begin{enumerate}
  \item Get the filename of the active file.
  \item If possible, save the file to disk if there has been any
    changes.
  \item Call the program `{\tt ChkTeX.rexx}' with the filename as the
    only parameter.
  \end{enumerate}

\item If somebody out there actually possesses (and uses) GoldED, it
  would be nice if they checked whether the ARexx script included
  actually work.  If not, please send me a fixed copy; perhaps also
  one which supports point 2 above, too. If it does work, then please
  tell me so, so I can remove this item.

  I don't have GoldEd in my possession; the script was just modelled
  after Juergen Zeschky's, ({\tt <juergen@sokrates.nbg.de>})
  $\mbox{PGP}\leftrightarrow\mbox{GoldED}$ interface.

\item If you have access to a dictionary listing abbreviations (not
  only English), I would appreciate an updated version of the \rsrc\
  file with these filled in.  In fact, if you update the \rsrc\ file
  in anyway that is not strictly local, I would appreciate to receive
  your updated version.

\item Suggestions for new warnings are always welcomed. Both formal
  (i.e.\ regexps or similar) and non-formal (plain English) descriptions
  are welcomed.
\end{itemize}

Of course, people doing any of this will be mentioned in this document, and
thus receive eternal glory and appreciation.

\subsection{Caps and stuff}

This program uses the {\tt getopt()} routine, as supplied from GNU\@.
The source included in this distribution has been modified slightly.
To make the use of C2LOCAL easier, portions which were
\verb@#ifdef@'ed out, have now been commented out.

Where trademarks have been used, the author is aware of that they
belong to someone, and has tried to stick to the original caps.

\section{About the author}

A quick summary of who I am and what I do:

I'm 20 years old, and live in Oslo, the capital of Norway.  I'm
currently studying maths and computer science at the
University~of~Oslo; planning to get a degree within mathematical
modelling, with a dash of physics and emphasing the computer part of
the study.  More precisely, in spring'96 my studies consist of
discrete mathematics, signal- and image-processing plus co-operating
in writing a program simulating the effects of acid rainfall in a
test-area in the south of Norway (the Birkenes-field, close to
Kristiansand).

At home I now possess 4 computers, of which 1 is regular use: A
vanilla Amiga 1200, expanded only by a HD\@.  The others are a {\tt
  80286} PC and an Amiga 500, both semi-out-of-order.  The last one is
a Commodore VIC-20, which for some peculiar reason never seems to be
used. Plans are to get a Linux-capable PC, though.

Most of the time in front of these computers (including SGI Indy's and
SPARC stations at our university) is spent on C and shell programming,
plus some textprocessing. 

% I am also involved in writing the document
% for {\sc Isaac} --- Interactive Simulation as an Alternative to
% Advanced Calculations.  This is planned to help newcomers to physics,
% by providing a computer program which enables one to simulate most
% experiments relating to classical mechanics.
%

C and shell programming are not my only knowledge areas regarding
computers, however.  I write the following languages more or less:
Perl, Motorola {\tt 68000} assembly code, ARexx, Simula, C++, \LaTeX,
HTML, AmigaGuide, Amos Basic and Installer LISP\@.  Once I also
mastered Commodore Basic V2 (the one included with my VIC-20 :-) ).

However, I also try to not to end up as a computer nerd.  Thus, in
addition to the obligatory (?) interest for computers, I am a scout.
Still running into the woods, climbing the trees, falling down and
climbing up once more, in other words.  To be more specific, I am a
now a troop leader for `Ulven' scoutgroup; Norwegian Scouts
Association.  I am also a active rover in `V�lerenga' scoutgroup.

If you {\em really\/} like this program, and wish to ensure that
development is continued, please consider sending one of the
scout-badges of your country.  It will surely be appreciated.
Remember, all this development is done on my spare time, and I 
would be very grateful for your initiative.

Certainly a lot more to tell (I play the piano and like cross-country
skiing, for instance); but I'll stop here before you fall
asleep\dots:-)


\section{Thanks}

The author wishes to thank the following people (in alphabetical order):

\def\Name#1#2{\item[]
\setbox0=\hbox{
\begin{tabular}{l}
\bf #1 \\
\tt #2 \\
\end{tabular}
} \usebox0\\ %par\noindent
}

\begin{description}

\Name{Russ Bubley}{russ@scs.leeds.ac.uk}
   He has been the main external beta-tester for this program, sending
   me loads and loads of understandable and reproducible bug reports.
   If you somehow think that \chktex\ is well-behaved and free from
   bugs, send warm thoughts to Russ. He has also provided ideas for
   enhanced checks and so forth.

   In addition, he sent me a huge list of 238 common English
   abbreviations, for inclusion in the \rsrc\ file! Together with the
   enhanced abbreviation recognizer, I do now believe most
   abbreviations should be catched\dots:-)

   Finally, he has also given me valuable hints for improving the
   program's outputting routine, and suggested enhanced methods for
   filtering unnecessary warnings away.

   \Name{Stefan  Gerberding}{stefan@inferenzsysteme.informatik.th-darmstadt.de}
   First one to report the Enforcer hit in v1.2 when using \chktex\ as
   a pipe.  Also came with suggestions to make \chktex\ more easily
   compile on early gcc compilers.

   He has also kept on beta-testing later versions of \chktex, giving
   me bug-reports and enhancements requests.

   \Name{Kasper B. Graversen}{kbg2001@internet.dk} Lots of creative
   suggestions and improvements.  5--6 of the warnings implemented
   were based on his ideas.

   \Name{Frank Luithle}{f\_luithle@outside.sb.sub.de}
   Wrote a translation for v1.0.  Unfortunately, he remained unreachable
   after that\dots :-/

   \Name{Nat}{nat@nataa.frmug.fr.net}
   Reported the same bug as Gerberding.  In addition, he taught me a
   few tricks regarding the use of gcc + made me understand that the
   ANSI standard isn't unambigious; at least the \verb@getenv()@ call
   seem to be open for interpretations.  Many possible
   incompatibilities have been removed due to these lessons.

   \Name{Michael Sanders}{sanders@umich.edu}
   Found a long-time bug in the \Cmd{command not intended} section.
   This one survived a few revisions, unfortunately (I haven't changed
   that part for quite a while).

   \Name{Bj\o rn Ove Thue}{bjort@ifi.uio.no}
   Author of the MSDOS port; please direct questions regarding
   strictly to that port to him (I would like to receive a carbon
   copy, though).

   \Name{Martin Ward}{Martin.Ward@durham.ac.uk}
   Sent a few bug-reports; also gave me information upon where to find
   regexp code. He also provided a few Perl scripts for inspiration
   and sent me the source code for \verb@lacheck@; which inspired some
   of the warnings.
\end{description}
\newpage

\section{Contacting the author}

If you wish to contact me for any reason ({\em scout-badges}, more tests,
bug reports, porting, suggestions, hellos, smiley's, etc.) or would like to
participate in the development of \chktex, please write to:

\begin{samepage}
\begin{quote}
  Jens Berger           \\*
  Spektrumvn. 4         \\*
  N-0666 Oslo           \\*
  Norway                \\*
  E-mail: {\tt <jensthi@ifi.uio.no>}
\end{quote}
\end{samepage}

Any signs of intelligent life is welcomed; that should exclude piracy.

Have fun.

\end{document}
